home *** CD-ROM | disk | FTP | other *** search
- Path: lrz-muenchen.de!news
- From: watzka@stat.uni-muenchen.de (Kurt Watzka)
- Newsgroups: alt.msdos.programmer,comp.lang.c,comp.lang.pascal.misc
- Subject: Re: typecasting preferences
- Date: 21 Apr 1996 12:30:23 GMT
- Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
- Distribution: world
- Message-ID: <4ld9ov$rek@sparcserver.lrz-muenchen.de>
- References: <4l020g$i9j@srvr1.engin.umich.edu> <Pine.A32.3.91.960416145209.106109C-100000@black.weeg.uiowa.edu> <4l4ldb$nkl@srvr1.engin.umich.edu> <3177866E.167E@wight.hursley.ibm.com>
- NNTP-Posting-Host: sun2.lrz-muenchen.de
-
- Max Waterman <dwater@wight.hursley.ibm.com> writes:
-
- >union Int_Over_Float {
- > Int integer;
- > Float floating_point;
- > };
- > typedef union Int_Over_Float Int_Over_Float;
-
- C _is_ case sensitive. There may be some local typedef standards that
- require you to have something like
-
- typedef int Int;
- typedef float Float;
-
- but I have never fully understood how this could help porting a program.
- If your code assumes that int is a 32-bit number, it's portability is
- restricted to 32-bit architectures, anyway. If you need a 32-bit type,
- why don't you ("You" is not Max Waterman in this case, but a less
- personal you) give it a name that documents that you assume that it
- will be a 32-bit type.
-
- Kurt
- --
- | Kurt Watzka Phone : +49-89-2180-6254
- | watzka@stat.uni-muenchen.de
-
-